Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1577

reference: 354-tree-1
name: 1577
tree-preservation-order: undefined
354-tpo-1
uprn
address-text
point: POINT (-1.045915 50.893562)
geometry: MULTIPOLYGON (((-1.045815 50.893552,-1.045820 50.893571,-1.045834 50.893589,-1.045855 50.893603,-1.045883 50.893612,-1.045914 50.893616,-1.045944 50.893613,-1.045972 50.893604,-1.045995 50.893590,-1.046009 50.893573,-1.046014 50.893553,-1.046010 50.893534,-1.045996 50.893516,-1.045974 50.893502,-1.045947 50.893493,-1.045916 50.893490,-1.045885 50.893493,-1.045858 50.893501,-1.045835 50.893515,-1.045821 50.893532,-1.045815 50.893552)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL